SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Library portal</title>

</head>

Library portal

</h1>

</header>

<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">A library portal is an interface to access <a href="Library" title="Library">library</a> resources and services through a single access and management point for users: for example, by combining the circulation and catalog functions of an <a href="Integrated_library_system" title="Integrated library system">integrated library system</a> (ILS) with additional tools and facilities.<a href="#cite_note-1">[1]</a>

/* start https://en.wikipedia.org/ */

@media all and (max-width:720px){body.skin-minerva .mw-parser-output .tocright{display:none}.mw-parser-output .tocright{width:100%!important}}@media all and (min-width:720px){.mw-parser-output .tocright{float:right;clear:right;width:auto;margin:0 0 0.5em 1em}.mw-parser-output .tocright-clear-left{clear:left}.mw-parser-output .tocright-clear-both{clear:both}.mw-parser-output .tocright-clear-none{clear:none}}

/* end https://en.wikipedia.org/ */

</style><div class="tocright"><meta property="mw:PageProp/toc"></div>

<div class="mw-heading mw-heading2"><h2 id="Definition">Definition</h2></div>

A library portal is defined as "a combination of software components that unify the user experience of discovering and accessing information" in contrast to a "single technology" to provide "services that support discovery, access and effective use of information."<a href="#cite_note-MaloneyBracke-2">[2]</a>

<div class="mw-heading mw-heading2"><h2 id="Major_elements">Major elements</h2></div>

In addition to the basic functions of access to the <a href="Library_catalog" title="Library catalog">library catalog</a>, and a user's subscription records, significant elements of a library portal normally include:

<ul><li>"<a href="Metasearch" class="mw-redirect" title="Metasearch">Metasearching</a> tools, browsable interfaces, and online reference help", which aid in the discovery process<a href="#cite_note-MaloneyBracke-2">[2]</a></li>

<li>Links to full-text articles, <a href="OpenURL" title="OpenURL">OpenURL</a>,</li>

<li><a href="Interlibrary_loan" title="Interlibrary loan">Interlibrary loan</a> (ILL) or document delivery, for material the library does not own</li>

<li><a href="Citation_management_software" class="mw-redirect" title="Citation management software">Citation management software</a>, user preferences services, "<a href="Knowledge_management" title="Knowledge management">knowledge management</a> tools"</li></ul>

More recently, the focus has been on the discovery goal, which has led to even more difficulties in defining a library portal. The terms "<a href="Discovery_tools" class="mw-redirect" title="Discovery tools">discovery tools</a>", "discovery services", "next-generation discovery tool", and "next-generation <a href="OPAC" class="mw-redirect" title="OPAC">OPAC</a>" are often used interchangeably.

<div class="mw-heading mw-heading2"><h2 id="Current_market">Current market</h2></div>

The focus on discovery tools has led to increased competitors in the discovery services market; the competitors that existed in the library portal market have also shifted their focus to this particular function.

A list of competitors in the current library portal market who have recently been awarded contracts by various libraries for their entire portal include  :

<ul><li>Axiell Arena: contract with The University of Gävle <a href="#cite_note-3">[3]</a></li>

<li>Axiell Calm: contract with Denmark's Roskilde Libraries for archive management <a href="#cite_note-4">[4]</a></li>

<li>BIBIS Library Portal: contract with ROC Mondriaan in The Hague <a href="#cite_note-5">[5]</a> as well as the library of the central bank of the Netherlands, the library of Provincie Zuid-Holland in South Holland, and at Dutch law firm Ploum Lodder Princen.<a href="#cite_note-6">[6]</a></li>

<li>ExLibris Primo: contract with Hesburgh Libraries of Notre Dame. Library Technology refers to this "discovery and delivery solution" as a "library portal".<a href="#cite_note-7">[7]</a></li>

<li><a href="MetaLib" title="MetaLib">MetaLib</a> Library Portal, ExLibris: contract with NASA's <a href="Johnson_Space_Center" title="Johnson Space Center">Johnson Space Center</a><a href="#cite_note-8">[8]</a></li></ul>

By contrast, the following list highlights contracts signed by libraries for specific discovery service tools, mostly at more recent dates

<ul><li>EOS.Web OPAC Discovery, EOS International: while it is unclear which of EOS services were purchased by their clients, the benefits to the EOS.Web OPAC Discovery grew significantly recently when EOS International signed an ILL agreement with the <a href="New_York_Law_Institute" title="New York Law Institute">New York Law Institute</a>, which will allow EOS clients to easily request NYLI union catalog items from their EOS.Web OPAC". EOS International's press releases do not specify which service was purchased but only mention the names of new clients.<a href="#cite_note-9">[9]</a></li>

<li>Summon, <a href="Serials_Solutions" title="Serials Solutions">Serials Solutions</a>: contract with <a href="University_of_Texas_at_Austin" title="University of Texas at Austin">University of Texas at Austin</a> Libraries,<a href="#cite_note-10">[10]</a> <a href="University_of_Connecticut" title="University of Connecticut">University of Connecticut</a> Libraries,<a href="#cite_note-11">[11]</a> <a href="University_of_Illinois_at_Chicago" class="mw-redirect" title="University of Illinois at Chicago">University of Illinois at Chicago</a> Library,<a href="#cite_note-12">[12]</a> <a href="California_State_University_System" class="mw-redirect" title="California State University System">California State University System</a>,<a href="#cite_note-13">[13]</a> <a href="Syracuse_University_Library" class="mw-redirect" title="Syracuse University Library">Syracuse University Library</a>,<a href="#cite_note-14">[14]</a> <a href="University_of_North_Carolina_at_Chapel_Hill" title="University of North Carolina at Chapel Hill">University of North Carolina at Chapel Hill</a> Library,<a href="#cite_note-15">[15]</a> <a href="Lund_University" title="Lund University">Lund University</a> Libraries,<a href="#cite_note-16">[16]</a> <a href="Helmut_Schmidt_University" title="Helmut Schmidt University">Helmut Schmidt University</a>,<a href="#cite_note-17">[17]</a> <a href="Peking_University" title="Peking University">Peking University</a>,<a href="#cite_note-18">[18]</a> <a href="University_of_the_Free_State" title="University of the Free State">University of the Free State</a>,<a href="#cite_note-19">[19]</a> <a href="Cornell_University" title="Cornell University">Cornell University</a> Library,<a href="#cite_note-20">[20]</a> <a href="Brown_University" title="Brown University">Brown University</a> Library,<a href="#cite_note-21">[21]</a> <a href="Kyushu_University" title="Kyushu University">Kyushu University</a> Library<a href="#cite_note-22">[22]</a></li>

<li>Ex Libris Primo and SFX OpenURL: contract with Online Dakota Information Network (Library Technology, March 27, 2012); <a href="Silesian_University_of_Technology" title="Silesian University of Technology">Silesian University of Technology</a>, Poland;<a href="#cite_note-23">[23]</a></li>

<li>EBSCO Discovery Service: contract with <a href="Seton_Hall_University" title="Seton Hall University">Seton Hall University</a>;<a href="#cite_note-24">[24]</a> <a href="Massey_University" title="Massey University">Massey University</a> Library, New Zealand;<a href="#cite_note-25">[25]</a> <a href="Warsaw_University" class="mw-redirect" title="Warsaw University">Warsaw University</a>, Poland;<a href="#cite_note-26">[26]</a> <a href="Bielefeld_University" title="Bielefeld University">Bielefeld University</a>, Germany;<a href="#cite_note-27">[27]</a> <a href="Biblioth%C3%A8que_nationale_de_France" title="Bibliothèque nationale de France">Bibliothèque nationale de France</a><a href="#cite_note-28">[28]</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Challenges">Challenges</h2></div>

When building a portal for a library, one of the challenges discussed by Morgan is communication: the building of a portal requires consensus with regards to what should be included.<a href="#cite_note-Morgan-29">[29]</a> Another challenge is ensuring a <a href="User-centered_design" title="User-centered design">user-centered design</a> for the portal. This involves conducting surveys, focus group interviews, and usability studies – all of which can be seen as time-consuming.<a href="#cite_note-Morgan-29">[29]</a> Additionally, compatibility with the hosting institution is critical.<a href="#cite_note-Morgan-29">[29]</a> Finally, the question of whether a library should go with <a href="Open_source_software" class="mw-redirect" title="Open source software">open source software</a> or commercial products is always a point of contention.

<div class="mw-heading mw-heading2"><h2 id="Standards">Standards</h2></div>

There are no accepted standards for library portals.<a href="#cite_note-30">[30]</a> The only standards in the literature are the more general search and retrieval standards, including <a href="Z39.50" title="Z39.50">Z39.50</a> and ZING (Z39.50-International: Next Generation), the <a href="Open_Archives_Initiative_Protocol_for_Metadata_Harvesting" title="Open Archives Initiative Protocol for Metadata Harvesting">Open Archives Initiative Protocol for Metadata Harvesting</a>, and <a href="OpenURL" title="OpenURL">OpenURL</a>.<a href="#cite_note-MaloneyBracke-2">[2]</a>

As a result of the lack of standards, and since customization is required in a library portal, individual institutions decide what they expect their portal to look like, and what services it will provide. For example, <a href="Harvard_University" title="Harvard University">Harvard University</a> is currently conducting a library portal project, which will begin implementation during the summer of 2012. They have identified their own list of criteria,<a href="#cite_note-31">[31]</a> which naturally differs substantially from the needs of other institutions. The various general areas that the committee has looked at include: content, user experience, features and capabilities, infrastructure and security, and search and discovery. It is uncertain which areas will be selected as part of the Phase I implementation of the portal.

<div class="mw-heading mw-heading2"><h2 id="Relationship_between_OPACs_and_library_portals">Relationship between OPACs and library portals</h2></div>

The <a href="Online_public_access_catalog" title="Online public access catalog">online public access catalog</a> (OPAC) is a basic module, part of the library's <a href="Integrated_library_system" title="Integrated library system">integrated library system</a>. Earlier, the OPAC has been limited to searching physical texts, and sometimes digital copies but has only limited special features. Caplan argues that they are in process of replacement by newer "discovery tools" allowing more customization.<a href="#cite_note-32">[32]</a> Yang and Hofmann suggest that vendors see money in building either separate discovery tools or Next-Generation OPACs to be purchased as an add-on feature.<a href="#cite_note-YangHofmann-33">[33]</a> A problem with vocabulary arises here. Yang and Wagner (2010, in Yang and Hofmann, 2011) refer to discovery tools by many names, including "stand-alone OPAC, <a href="Discovery_layer" class="mw-redirect" title="Discovery layer">discovery layer</a>, and next-generation catalog [sic.]"<a href="#cite_note-YangHofmann-33">[33]</a> This contrasts Bair, Boston, and Garrison, who differentiate between next-generation catalogues and web-scale discovery services.<a href="#cite_note-34">[34]</a> Despite any confusion, it is clear that the OPAC as it currently stands is outdated, and will be replaced by more modern, user-friendly tools. The next-generation OPAC as described by Yang and Hofmann will ideally have the following 12 features (although not all features are currently available in any single discovery product):<a href="#cite_note-YangHofmann-33">[33]</a>

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col">

<ul><li>Single point of entry for all library resources</li>

<li>State-of-the-art <a href="Web_interface" class="mw-redirect" title="Web interface">web interface</a></li>

<li>Enriched content</li>

<li><a href="Faceted_navigation" class="mw-redirect" title="Faceted navigation">Faceted navigation</a></li>

<li>Simple keyword search box with a link to advanced search on every page</li>

<li>Relevancy ranking</li>

<li>Spell-checking</li>

<li>Recommendations/related materials</li>

<li>User contribution</li>

<li><a href="RSS" title="RSS">RSS</a> feeds</li>

<li>Integration with social networking sites</li>

<li>Persistent links</li></ul>

</div>

<ul><li><a href="Digital_information" class="mw-redirect" title="Digital information">Digital information</a></li>

<li><a href="Library_science" class="mw-redirect" title="Library science">Library science</a></li>

<li><a href="Web_portal" title="Web portal">Web portal</a></li></ul>

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFMichalak2005" class="citation book cs1">Michalak, Sarah, ed. (2005). Portals and Libraries. Binghamton, NY: <a href="Haworth_Press" title="Haworth Press">Haworth Press</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0789029316</bdi>. <a href="OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/57564758">57564758</a>.</cite>

</li>

<li id="cite_note-MaloneyBracke-2">^ <a href="#cite_ref-MaloneyBracke_2-0">a</a> <a href="#cite_ref-MaloneyBracke_2-1">b</a> <a href="#cite_ref-MaloneyBracke_2-2">c</a> <cite id="CITEREFMaloneyBracke2005" class="citation journal cs1">Maloney, K; Bracke, P.J. (2005). "Library portal technologies". Journal of Library Administration. 43 (1–2): 87–112. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1300%2FJ111v43n01_07">10.1300/J111v43n01_07</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:57092745">57092745</a>.</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> Library Technology, January 11, 2011

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> Library Technology, November 25, 2010

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> Library Technology, July 1, 2008

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> Library Technology, February 19, 2008

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> Library Technology, June 19, 2008

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> Library Technology, November 13, 2006

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> Library Technology, April 16, 2012

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> Library Technology, April 6, 2012

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, February 29, 2012, retrieved February 6, 2013

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> Library Technology, February 1, 2012

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> Library Technology, January 18, 2012

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> Library Technology, January 13, 2012

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, January 10, 2012, retrieved February 6, 2013

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, December 15, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, November 29, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, November 22, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, November 17, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, October 20, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, August 18, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <a rel="nofollow" class="external text" href="http://www.librarytechnology.org">www.librarytechnology.org</a>, August 1, 2011, retrieved February 6, 2013

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> Library Technology, February 8, 2012

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> Library Technology, March 27, 2012)

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> Library Technology, March 20, 2012

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> Library Technology, March 13, 2012

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> Library Technology, February 2, 2012

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> Library Technology, January 10, 2012

</li>

<li id="cite_note-Morgan-29">^ <a href="#cite_ref-Morgan_29-0">a</a> <a href="#cite_ref-Morgan_29-1">b</a> <a href="#cite_ref-Morgan_29-2">c</a> <cite id="CITEREFMorgan2005" class="citation journal cs1">Morgan, E.L. (2005). <a rel="nofollow" class="external text" href="https://doi.org/10.1002%2Fbult.1720310112">"Portals in libraries: Portal implementation issues and challenges"</a>. Bulletin of the American Society for Information Science and Technology. 31: 22–23. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1002%2Fbult.1720310112">10.1002/bult.1720310112</a>.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite id="CITEREFSadehWalker,_J.2003" class="citation journal cs1">Sadeh, T; Walker, J. (2003). "Library portals: Toward the semantic web". New Library World. 104 (1184/1185): 11–19. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1108%2F03074800310458241">10.1108/03074800310458241</a>.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://archive.today/20121211100845/http://isites.harvard.edu/icb/icb.do?keyword=k77982&pageid=icb.page497421">"Library portal high-level requirements: identified through discussion with library staff"</a>. Harvard University. Archived from <a rel="nofollow" class="external text" href="http://isites.harvard.edu/icb/icb.do?keyword=k77982&pageid=icb.page497421">the original</a> on 11 December 2012. Retrieved 17 April 2012.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> <cite id="CITEREFCaplan2012" class="citation journal cs1">Caplan, P (2012). "On discovery tools, OPACs and the motion of library language". Library Hi Tech. 30 (1): 108–115. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1108%2F07378831211213247">10.1108/07378831211213247</a>.</cite>

</li>

<li id="cite_note-YangHofmann-33">^ <a href="#cite_ref-YangHofmann_33-0">a</a> <a href="#cite_ref-YangHofmann_33-1">b</a> <a href="#cite_ref-YangHofmann_33-2">c</a> <cite id="CITEREFYangHofmann2011" class="citation journal cs1">Yang, S.Q.; Hofmann, M.A. (2011). "Next generation or current generation?: A study of the OPACs of 260 academic libraries in the USA and Canada". Library Hi Tech. 29 (2): 266–300. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1108%2F07378831111138170">10.1108/07378831111138170</a>.</cite>

</li>

<li id="cite_note-34"><a href="#cite_ref-34">^</a> <cite id="CITEREFBlairBoston,_G.Garrison,_S.2011" class="citation journal cs1">Blair, S.A.; Boston, G.; Garrison, S. (2011). <a rel="nofollow" class="external text" href="http://scholarworks.wmich.edu/library_pubs/21">"Taming lightning in more than one bottle: Implementing a local next-generation catalog versus a hosted web-scale discovery service"</a>. University Libraries Faculty & Staff Publications. Retrieved 17 April 2012.</cite>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a href="https://en.wikiversity.org/wiki/1-b:_History_of_digital_libraries,_and_library_automation" class="extiw external" title="v:1-b: History of digital libraries, and library automation">History of Library Automation</a> – Wikiversity</li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-04-03" href="https://en.wikipedia.org/wiki/?title=Library_portal&oldid=1283837700">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>